With few exceptions, data groups must be defined in a device template file in order for them to be available for use on a remote device. Which data groups are defined by a device template file depends on protocol, device type, and unique configuration.
CygNet distributes sample device template files for its EIEs, each of which typically serves one or more hardware models along with applicable firmware. Therefore, the data groups described below are only those data groups defined by CygNet in sample device template file(s). Your template(s) might not include some of the data groups described below. Device template files exist to enable users to customize device configurations; however, CygNet is not responsible for changes made by users.
For information about data group definitions and device template files, see Device Template Files.
For more information about data group dependencies, see Data Group Dependencies.
| Data Group Type | Usage Notes |
|---|---|
|
"Gas Analysis Config" |
|
|
AgaCfg |
"Aga Configuration" |
|
CfgMB |
|
|
The "Composite Data Group" is a special kind of data group that enables you to combine any data group element(s) from any data group(s) as long as they are in the same template as the composite data group. The "Composite Data Group" does not appear in a remote device editor unless it has been defined in the relevant device template file. See Composite Data Group. |
|
|
CHstGDRecD |
"Cur Gas Diff Hist (daily)" |
|
CHstGDRecH |
"Cur Gas Diff Hist (hrly)" |
|
CHstGPRecD |
"Cur Gas Pulse Hist (daily)" |
|
CHstGPRecH |
"Cur Gas Pulse Hist (hrly)" |
|
CHstLDRecD |
"Cur Liquid Diff Hist (daily)" |
|
CHstLDRecH |
"Cur Liquid Diff Hist (hrly)" |
|
CHstLPRecD |
"Cur Liquid Pulse Hist (daily)" |
|
CHstLPRecH |
"Cur Liquid Pulse Hist (hrly)" |
|
CtrlCfg |
A valid "Controller Configuration" data group must be retrieved before other data groups can be retrieved or sent. |
|
CtrlInfo |
"Controller Info" |
|
"FMS Legacy Config Send Data" This data group depends on supporting data groups to be defined in order for successful transactions to be completed. |
|
|
"FMS Legacy Configuration Data" must be retrieved before other FMS Legacy data groups of the same ordinal can be retrieved. This data group depends on supporting data groups to be defined in order for successful transactions to be completed. |
|
|
"FMS Legacy History Data" This data group depends on supporting data groups to be defined in order for successful transactions to be completed. |
|
|
"History - Daily" |
|
|
"History - Hourly" |
|
|
"Meter Config" |
|
|
"Single Read-Only Coil" Only one instance of this data group allowed. |
|
|
"Single Read/Write Coil" Only one instance of this data group allowed. |
|
|
"Single R/O Register" Only one instance of this data group allowed. |
|
|
"Single R/W Register" Only one instance of this data group allowed. |